Providing information to a mobile device based on an event at a geographical location

ABSTRACT

A system, method, and computer readable medium for providing information to a mobile device based on an event comprising detecting an occurrence of the event, determining if the event is a specific event and if the event occurred at or near a geographical location and sending an alert of the event to at least one mobile device if the event is the specific event, if the event occurs at or near the geographical location, and if the at least one mobile device is located at or near the geographical location.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.14/508,479, entitled PROVIDING INFORMATION TO A MOBILE DEVICE BASED ONAN EVENT AT A GEOGRAPHICAL LOCATION, filed on Oct. 7, 2014, which is acontinuation of U.S. application Ser. No. 13/794,095, entitled PROVIDINGINFORMATION TO A MOBILE DEVICE BASED ON AN EVENT AT A GEOGRAPHICALLOCATION, filed on Mar. 11, 2013, now issued U.S. Pat. No. 8,855,683,issued on Oct. 7, 2014, which is a continuation of U.S. application Ser.No. 13/187,834, entitled PROVIDING INFORMATION TO A MOBILE DEVICE BASEDON AN EVENT AT A GEOGRAPHICAL LOCATION, filed on Jul. 21, 2011, nowissued U.S. Pat. No. 8,412,231, issued on Apr. 2, 2013, which claimspriority from U.S. provisional application Ser. No. 61/370,265, entitledPROVIDING INFORMATION TO A MOBILE DEVICE BASED ON AN EVENT AT AGEOGRAPHICAL LOCATION, filed on Aug. 3, 2010. U.S. application Ser. No.13/187,834 is also a continuation-in-part of U.S. application Ser. No.12/150,413, titled PROVIDING INFORMATION TO A MOBILE DEVICE BASED ON ANEVENT AT A GEOGRAPHICAL LOCATION, filed on Apr. 28, 2008, now issuedU.S. Pat. No. 8,219,110, issued on Jul. 10, 2012. The entire contents ofeach are incorporated by reference herein.

FIELD OF THE INVENTION

The present disclosure is generally related to a communications network,and more particularly to providing information to a mobile device basedon an event at a geographical location in a communications network andto monitor persons moving through or by a geographic location via theircellular device signals.

BACKGROUND OF THE INVENTION

When an event occurs in a specific location, government agencies thatrespond to or are responsible for the event may send out alerts tonearby entities with details about the event. In this way, others maytake preventative actions against the event. For example, an accidentmay have occurred at a busy interchange of highways. Currenttransportation authorities who monitor traffic flows may send out textalerts to electronic signals positioned at various highways to alertdrivers nearby. Drivers who saw the text alert may then takepreventative actions against the event, for example, by taking analternate route.

By sensing distinct signals from cellular devices, one can detect thenumber of ambient device near a particular point. There isn't need tounderstand the content of the signals only that the distinct signalsexist. Much like a radar detector, a WIFI signal detector, etc,inexpensive devices can be constructed which detect ambient distinctsignals and can determine their number. By knowing the number, amonitoring system could be configured to detect changes in signal countwhich shows cellular devices in particular, but might in general reflectan group of individuals trespassing, increased car traffic, unauthorizedor unknown gatherings of individuals. Using this knowledge, a systemcould be configured to extend warnings and notices electronically toparties that would interest in such events, as in a Homeowner'sAssociation, security companies, anyone interested in inferring adetectable change in the number of individuals in a given area.

While current systems adequately alert events to people nearby, theyfail to provide alerts to those who are on the move, for example, thosewho are not in the nearby area but are approaching the event location.This failure is due to the limitation of current systems, which providealert information only to fixed locations, such as pre-installedelectronic signals or wired telephone lines. Therefore, what is neededis ability to provide information to those who are not fixed inposition, for example, mobile device users, no matter where they ortheir devices are geographically located.

SUMMARY OF THE INVENTION

The present disclosure describes a method for providing information to amobile device based on an event at a geographical location. Anoccurrence of an event is detected. A determination is made as towhether the event is a specific event and if the event occurred at ornear a geographical location. If the event is the specific event, occursat or near the geographical location, and if the at least one mobiledevice is located at or near the geographical location, an alert of theevent is sent to at least one mobile device.

In one embodiment, the detection of the event comprises sensing by asensor an occurrence of an event above a predetermined threshold.Alternatively, the detection comprises capturing information about theevent by at least one mobile device, sending the information to at leastone service provider site, and forwarding the information to arepository.

In order to send an alert to the at least of mobile device, informationabout the event is first processed. An image is recognized from theinformation about the event, a type of the event is identified based onthe image, and a location of the event is identified based on a locationof the at least one mobile device.

When sending an alert of the event to at least one mobile device, in oneembodiment of the present disclosure, a lookup of at least one mobiledevice associated with at least one service provider site is performed.The alert is then sent to the at least one mobile device associated withthe at least one service provider site. In an alternative embodiment,the alert is sent to at least one service provider site. The alert isthen forwarded from the at least one service provider site to at leastone mobile device associated with the at least one service providersite.

In yet another embodiment of the present disclosure, a lookup of atleast one mobile device associated with at least one service providersite is performed. A location of the at least one mobile device isidentified. The alert is then sent to the at least one mobile devicewithin a predetermined distance of the event based on the location.

In still yet another embodiment of the present disclosure, a location ofat least one service provider site is identified from a geographicalinformation system. The alert is sent to the at least one serviceprovider site within a predetermined distance of the event based on thelocation. The alert is then forwarded from the at least one serviceprovider site to at least one mobile device associated with the at leastone service provider site.

In addition to sending alert messages based on geographical locations,the alert may be sent to the at least one mobile device based on aperiod of time the at least one mobile device is registered with aservice provider site.

In a further embodiment of the present disclosure, a communicationsnetwork for providing information to a mobile device based on an eventat a geographical location is provided. The communications networkcomprises at least one mobile device utilized by at least one mobileuser, at least one service provider site associated with the at leastone mobile device; and an event alert system operable to detect anoccurrence of the event, process information related to the event, andsend an alert of the event to the at least one mobile device if theevent is a specific event, if the event occurs at or near a geographicallocation, and if the at least one mobile device is located at or nearthe geographical location.

The embodiment of the present disclosure also allows for a sensor orsensors attuned to detecting cell phone or other mobile or wirelessdevice signals as point source interfaces with a service center thatthrough human intervention or algorithmic design can decide when to sendalerts based on the change in ambient signals detected within thesensor's area. A threshold change allows the service center to issuealerts and recipients to effect a response.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts one illustrative embodiment of a communications networkfor providing information to mobile device based on an event at ageographical location.

FIG. 2 depicts an alternative embodiment of a communications network forproviding information to mobile device based on an event at ageographical location.

FIG. 3 depicts a flowchart of a method for providing information tomobile device based on an event at a geographical location.

FIG. 4 depicts a flowchart of one exemplary method for sending alertmessages directly to mobile devices.

FIG. 5 depicts a flowchart of one exemplary method for indirectlysending alert messages to mobile devices.

FIG. 6 depicts a flowchart of an exemplary method for detecting theevent from a mobile device.

FIG. 7 depicts a flowchart of one exemplary method for processing theinformation in a repository or database.

FIG. 8 depicts a flowchart of an exemplary method for providinginformation to a mobile device which initiated event monitoring.

FIG. 9 depicts a typical configuration in a simplified diagram. FIG. 9depicts a sensor mounted atop a camera pole. The sensor in thissimplified example detects distinct signals from Devices 200. The links(logical and physical) between the Event Monitor [Device 102] softwarewhich resides on the Event Alert System [Device 108]. Also representedis a logical diagram of Device 108 notifying User 112 via SMS TXT toMobile Device 114 or via voice call through the Mobile Carrier network[Device 116].

FIG. 10 depicts a possible sample event log. The Browser Interface EventAlert System would display and allow for categorization of events,setting of alarms, notifications, etc. There would be an Item columnwhich depicts the Sensor being tied to a trigger. There might, forexample, be a Peak Value Change (delta) in distinct signals detected, atime limit, notification party, and a method to effect the notification.

FIG. 11 depicts a Browser Alert System Interface.

DETAILED DESCRIPTION OF THE INVENTION

Referring now to FIG. 1, one illustrative embodiment of a communicationsnetwork for providing information to mobile device based on an event ata geographical location is depicted. In communications network 100,event monitor 102 is responsible for monitoring events 104 that occur invarious geographical locations. Examples of event monitors includegovernment or municipal agencies, such as police, fire departments,public safety answering points, and the like. Examples of events beingmonitored include a traffic accident, a construction detour, anexplosion, a fire, a police pursuit, and the like.

Event monitor 102 may recognize events 104 by using operators or sensors106 that are installed at the various geographical locations fordetecting the occurrence of events 104. Examples of events that sensors106 may detect include earthquakes, rain storms, electricity outage, andthe like. In addition to sensors 106 that are installed at variousgeographical locations, sensors 106 may be installed within the eventmonitor 102 for monitoring events that occur above a predeterminedthreshold. For example, sensors 106 may be installed at the eventmonitor 102 to detect vibrations above a predetermined threshold toalert an earthquake.

When the event monitor 102 detects or senses an event 104, the eventmonitor 102 notifies an event alert system 108. The event alert system108 stores the event 104 in a repository or database 110 and determinesif the event is a specific event and if the event occurs at or near ageographical location. The event alert system 108 determines whether theevent is a specific event based on a type and/or location of the event.

If the event is a specific event and if the event occurs at or near ageographical location, the event alert system 108 provides informationrelated to the event to mobile devices 114 at or near the geographicallocation. In one illustrative embodiment, the event alert system 108alerts the mobile device 114 by directly sending alert messages tomobile device 114. In order to send alert messages directly to mobiledevice 114, the repository or database 110 may comprise information ofmobile device 114 at or near the geographical location. For example,repository or database 110 may comprise a table of mobile identificationnumbers (MINs) associated with service provider sites 116 at or near thegeographical location. A mobile identification number (MIN) uniquelyidentifies a mobile device in a service provider network.

While alerts may be sent to mobile device 114 at or near thegeographical location, the event alert system 108 may sent alerts tomobile devices 114 that are within a certain distance of the event 104.To determine the location of mobile device within a geographical area,the event alert system 108 may consult data stored within thegeographical information system (GIS) or global positioning system (GPS)118. For example, alerts may be sent to mobile device that are within acertain number of feet, miles, or yards of the event. In this way, onlymobile devices 114 that are located within a certain distance of ageographical area affected by the event 104 may be alerted. Nodisruptions will be caused to the other devices.

In an alternative embodiment, the event alert system 108 may alert themobile device 114 by sending alert messages to service provider sites116 or other systems at the geographical location or within a certaindistance of the event 104. Since each service provider site 116 keepstrack of its mobile device 114 with their mobile identification numbers(MINs), no mobile device information will be stored in the repository ordatabase 110. However, to determine service provider sites located at ageographical location or within a certain distance of the event, theevent alert system 108 may consult data stored within the geographicalinformation system (GIS) or global positioning system (GPS) 118. Inresponse to receiving alert messages from the event alert system 108,service provider sites 116 forward the alert messages to its mobiledevices 114, which in turn notify their mobile users 112.

The event alert system 108 may instruct service provider sites 116 tosend a specific message to a mobile device 114 based on its location andheading relative to the event. For example, service provider sites 116may send alert message A to mobile device 114 that are moving towardsthe event 104. Service provider sites 116 may also send alert message Bor no alert message at all to mobile device 114 that are moving awayfrom the event 104. In order to detect mobile device's location andheading relative to the event, the event alert system 108 may consultdata stored within GIS/GPS system 118. In addition, service providersites 116 may detect the received signal strength indication (RSSI) ofits mobile devices 114 and determine their locations and headingsrelative to the event. Alternative to a specific message, the eventalert system 108 may also instruct service provider sites 116 to send ageneric alert message to all associated mobile device 114 withinformation related to the event 104.

Alternative to detecting events by event monitor 102, events may bedetected by the event alert system 108 from a reporting of the eventoriginated from a person involved in the event or bystanders. FIG. 2provides an alternative embodiment of a communications network forproviding information to mobile device based on an event at ageographical location. In communications network 200, a person involvedmay capture information of the event 204 with mobile device 214. Forexample, mobile user 212 may take a picture of a scene of the accidentwith mobile device 214. Other examples of information captured by themobile user 212 include videos, graphics, sounds, and the like.

Mobile user 212 may then report the event by sending the eventinformation from mobile device 214 to the event alert system 208 viaservice provider sites 216. In response to receiving the eventinformation, the event alert system 208 stores the event information inrepository or database 210. Based on the event information, the eventalert system 208 may utilize the GIS/GPS system 218 and imagerecognition software 220 to identify the location and/or the type of theevent 204. The location, the type or a combination of the location andtype of the event identifies the event as a specific event. The eventalert system 208 then sends alert messages directly to mobile devices214 at the geographical location or within a certain distance of theevent 204. Alternatively, the event alert system 208 may send alertmessages to service provider sites 216 at or near the geographicallocation or within a certain distance of the event 204. In response toreceiving alert messages from the event alert system 108, serviceprovider sites 216 may forward the alert messages to associated mobiledevices 214, which in turn notify their mobile users 212.

FIG. 3 provides a flowchart of a method for providing information tomobile device based on an event at a geographical location. Process 300begins at step 302 with detecting occurrence of an event. In oneembodiment, the event may be detected using sensors. Alternatively, aperson involved or bystanders may report an event by capturing eventinformation with mobile devices. Next, the process continues to step 304to determine if the event is a specific event, if the event occurs at ornear a geographical location. The process then completes at step 306 tosend alert messages either directly or indirectly to mobile devices ifthe event is a specific event, if the event occurs at or near ageographical location, and if the mobile device is at or near thegeographical location.

FIG. 4 provides a flowchart of one exemplary method for sending alertmessages directly to mobile devices. The process 306 begins at step 402with performing a lookup of mobile devices associated with serviceprovider sites based on their mobile identification numbers (MINs). Inthis example, the lookup may be performed at the service provider sites.Next, the process continues step 404 to determine whether alert messagesshould be sent to all mobile device at a geographical location or withina certain distance of the event.

If alert messages are to be sent to mobile devices at a geographicallocation, the process continues to step 406 to send alert messages toMINs associated with service provider sites at the geographicallocation. However, if alert messages are to be sent to mobile deviceswithin a certain distance of the event, the process continues to step408 to consult locations of mobile devices from data stored within aGIS/GPS server and completes at step 410 to send alert messages to MINswithin a certain distance of the event.

FIG. 5 provides a flowchart of one exemplary method for indirectlysending alert messages to mobile devices. Process 306 begins with step502 with determining whether alert messages should be sent to all mobiledevices at a geographical location or within a certain distance of theevent. If alert messages are to be sent to all mobile devices at ageographical location, the process continues to step 504 to send alertmessages to service provider sites that are located at the geographicallocation. Subsequently, the process continues to step 506 to forwardalert messages to MINs associated with the service provider sites.

However, if alert messages are to be sent to all mobile devices within acertain distance of the event, the process continues to step 508 toconsult locations of service provider sites from data stored within aGIS/GPS server and to step 510 to forward alert messages to serviceprovider sites that are within a certain distance of the event. Theprocess 306 then completes at step 506 to forward alert messages to MINsassociated with the service provider sites located within a certaindistance of the event.

As discussed above, instead of using sensors to detect occurrence ofevents, a person involved or bystanders may report event informationusing their mobile devices. FIG. 6 provides a flowchart of an exemplarymethod for detecting the event from a mobile device. The process 302begins at step 602 with a mobile user capturing information of the eventwith a mobile device. Next, the process 302 continues to step 604 tosend the captured event information from a mobile device to a serviceprovider site. The process 302 then completes at step 606 to forward thecaptured event information from the service provider site to the eventalert system. Once the captured event information is received, the eventalert system may store and process the information in a repository ordatabase.

FIG. 7 provides a flowchart of one exemplary method for processing theinformation related to the event in a repository or database. Theprocess 304 begins at step 702 with recognizing an image from thecaptured event information. To accomplish this step, the captured eventinformation may be compared to images stored within an image recognitionsoftware system. For example, the scene of an accident may be recognizedby the image recognition software by comparing it to images ofintersections stored within the image recognition software system.

Next, the process 304 continues to step 704 to identify a type of theevent based on the recognized image. To accomplish this step, theinformation from the captured image may be compared to informationstored within the repository or database. For example, the accidentscene image recognized by the software may be compared to informationstored within the repository or database and an accident event isidentified. After the type of event is identified, the process 304continues to step 706 to identify location of the event based on thelocation of the mobile device reporting the event or a recognized image.To accomplish this step, the event alert system may consult data storedwithin a GIS/GPS server. Based on the type, the location, or acombination of the type and location of the event, alert messages may besent to mobile devices that are at or near the geographical location.

In addition to alerting events to mobile devices based on geographicallocation, alert messages may be sent based on time periods spent bymobile users in a particular geographical location. For example, alertmessages may be sent only to mobile devices that have passed through orare registered with a service provider site within a certain period oftime. Examples of periods of time include months, weeks, days, hours,minutes, and the like. In this way, alerts may be sent to mobile devicesthat are within the reach of a service provider site for a specificperiod of time. For example, if an accident occurred in a particulargeographical location half an hour ago, alert messages may be sent tomobile device that have passed through or are registered with a serviceprovider site located within a certain distance of the event for thepast half hour, such that mobile users in the vicinity of the accidentmay take preventative action to avoid the scene. In order to identifymobile devices based on a period of time, it is preferable to storemobile identification numbers (MINs) associated with each serviceprovider site for a period of time in the service provider site, arepository, or a database.

It is noted that the alert messages being sent to the mobile devices mayinclude information related to the event in a form of text, voice,sound, graphics, email, short messages, and the like. In the event thata short message alert is sent, the message may be sent via a shortmessage servicing center. In addition to text alerts, alert messages mayinclude additional information about the event. For example, the alertmessage may include a link to obtain further information related to theevent, a link to a map surrounding the location of the event, asuggestion of alternate route, etc. Furthermore, additional informationabout the event may include instructions from government agenciesindicating precautions to take against the event. For example, theHomeland Security Department may send out information about theprocedures for dealing with nuclear, biological, and chemical events.

Moreover, different types of alert messages may be sent based on thetype of events that occurred. For example, short message type 1 (SMS1)may be sent for a general event, while short message type 2 (SMS2) maybe sent for a more serious event. In addition, one or more types ofmessages may be sent simultaneously to a mobile device based on the typeof events. For example, in an event of abduction, a text containing alicense number and description of the abductor may be sentsimultaneously with a picture of the abductee and a map of the abductionlocation.

In addition to initiating event monitoring by an event monitor or aperson involved in the event, mobile users may register for monitoringof events and delivery of alert messages when the events occur. FIG. 8provides a flowchart of an exemplary method for providing information tomobile device who initiated event monitoring. Process 800 begins at step802 with a mobile user registering a location and/or type of event to bemonitored. For example, a mobile user may register to monitor for atraffic accident at a particular intersection.

Next, process 800 continues to step 804 to monitor for the specificevent.

Process 800 continues to step 806 to determine if the event is aspecific event based on the type and/or location of the event detected.This step may be accomplished by utilizing the GIS/GPS system and imagerecognition software. If the event is the specific event based on thelocation and/or type of the event detected, process 800 continues tostep 808 to send messages alerting the event either directly orindirectly to the mobile device of the registered user. Otherwise, theprocess terminates thereafter.

In summary, aspects of the present disclosure provide a method andsystem for providing information to mobile device(s) based on an eventat a geographical location. Events may be detected from sensors orreporting of the event by a person. Also, a mobile user may register andinitiate event monitoring. Alerting of the events may be performeddirectly or indirectly. Alert messages may be sent directly to mobiledevices that are associated with service provider sites in variousgeographical locations. Alert messages may also be sent first to theservice provider sites or other systems, which then forward the messagesto associated mobile devices. Event information may be stored in arepository or database or within the service provider sites. Aspects ofpresent disclosure may utilize image recognition software and GIS/GPSservers to identify a location and a type of the event, such that adetermination can be made as to whether the event is a specific event.In this way, alert messages may be sent to specific mobile devices at ornear the geographical location of the event.

In additional embodiments, the ability to trigger dynamically upon thechange in the number of distinct cell phones and to initiate someresponse is an embodiment of the instant application. Triggers are basedupon change in the ambient background and by their nature indicate achange of static events occurring within a predetermined sensed area. Inaddition to alerting events to mobile devices based on geographicallocation, alert messages may be sent based on detections or changes inspecified measurements. Referring now to FIG. 9, sensor 106 may be adevice to detect the number of distinct mobile signals passing a certainpoint or within detection of a sensor. For example, sensor 106 iscapable of detecting electronic emissions from cell phone bandfrequencies. This capability to detect is analogous to radar detectors,spectrum analyzers, etc. Components within the device detect emissionswithin the known cellular frequencies of the area. These are regulatedand well defined. Camera 201 is a device that captures images within itsoperating range. Device(s) 200 are multiple cell phones possibly ofdifferent model, type, and service provider. When Sensor 106 detectssignals (or electronic emissions) from device(s) 200, it relays inreal-time a signal count to the Event Monitor 102. This detection mightbe in the form of the regular registrations that a cell phone isrequired to make in order to keep its service tower cognizant of thecell phone's location. This signal burst is not necessarily decoded,just detected. Device 102 then determines the location of the sensor andother event identifying information that might be programmed by thedesigner or implementer of the system, and passes that information tothe Event Alert System 108. The location of the device might be static(permanently mounted) or mobile and can be provided via GPS.

Device 108 then compares the information received against a set oftriggers and rules that have been selected by the implementer of thesystem. This information would be a count of the active signals itdetects within its sensing area. The sensor itself doesn't managetriggers, it only sends the changes sensed in its environment. At theEvent Alert System, if according to these predetermined rules aqualifying event is detected (such as there being a sudden jump of anumber of devices 200 detected, for example three or more), or a drop inthe number of signals, etc.) then Device 108 alerts individuals or logsthe event based upon preferences provided by the implementer (such asSMS to an individual or by entering a log entry in to an event log).Other devices in FIG. 9 are device 110 (Repository/DB) a Repository orDatabase where the history of sensor messages are stored. Also in FIG.9, a GIS/GPS system is tied to the location of Sensors like 106 andothers of its type. This GPS system may provide moving maps to allow formobile sensors, but also to interface with external systems, such asSecurity summoning systems (not shown), etc.

The sensor detects distinct point sources of EMI from cell phones(distinct cell bands) analogous to RADAR detectors, WiFi detectors, andspectrum analyzers. The signals are not interpreted or examined exceptfor detection of their existence. The Sensor may then be configured tonotify the Event Alert System when a threshold is passed. There is aweb-based interface allowing configuration of the device. Ultimateprotocol to the sensor is preferably HTTPS but may be another protocolsuitable for sending and receiving information. The sensor has embeddedHTTPS parsing capabilities.

FIG. 9 shows an example system for a Neighborhood Alert integratedwithin the Neighborhood's Security Cameras. The Event Alert System 108in FIG. 9 can be set to note what the background number of cell signalsare (such as the number of homes nearby and the cell signals thatemanate from these homes). Within the Web Interface, the sensor canrelay the number of detected signals at any given time. Since cell phonespectrum is strictly confined, there is limited spectrum to recognizefor locating mobile signals. Then, when there is a change from thebackground number or level to some quantitatively larger valuedetermined from a set of rules provided in the EVENT SERVER, anotification is sent.

The Event Server may be located in a datacenter, or as a logicalcomponent of a larger computing device or shared algorithmic device. TheEvent Alert System will provide notification based on rules configuredvia software located on the Event Alert System and managed via acraftsperson or responsible and trained user and/or system implementer).Referring now to FIG. 10, based on such rules (which may bepreconfigured or currently configured), the appropriate persons,devices, email accounts, pagers, etc. are notified. This is significantin that using cameras to detect scenery or heat signature or otherdetection systems leads to high false positives (authorized and expectedpersons returning home, pets, wind, weather, etc). Using the ubiquitouspresence of mobile phones to track groups of individuals allows a highlyselective warning conf FIG. 10 shows a sample view of the BrowserInterface Event Alert System (BIEAS). This is a possible configurationand view of a configuration and notification tool. This sample tableshows a hypothetical sensor sampling of Sensor 106, Sensor 106 a, Sensor108, Sensor 106 b. The BIEAS shows a possible column tracking of Item,Column Peak Value Change (DELTA), Within (seconds), Column Notify,Column Method. Column Item refers to a unique sensor within eachconfiguration or purview of the BIEAS instantiation. Column Peak ValueChange (DELTA) refers to a possible trigger point for notificationaction. The DELTA refers to a change in the number of distinct signalswithin a period of time (COLUMN WITHIN). Column NOTIFY provides a targetnotification address. Here target address can be phone number, emailaddress, text address, and so on. METHOD relates to how to invoke thetarget address (SMS, email, Voice message, etc.)

For the sample BIEA chart in FIG. 10, the first row refers to Sensor106. It is assigned a Peak Value Change of 3 within 10 seconds. In thisgeneric example, that would mean that when Sensor 106 detects a changein signals of 3 from the normal background count. Normal backgroundcount can be established via a rolling average (distinct counts in thelast 10 sampling periods [Within Seconds column]) or via an input value(assigned value). When Sensor 106 detects a change equal to or greaterthan the Peak Value Change, an alert is generated. Following onto theNOTIFY column, here number 2142445555 is notified via the METHOD of SMStext that “SENSOR 106 DELTA REACHED”

For Sensor 106 a, the DELTA change is 10 signals and the notificationgoes to an email address. For Sensor 108, a phone number receives arecorded or synthesized voice message. For 106 b an SMS message.

The Browser Interface Event Alert System may have multiple interfaces tofacilitate different kinds and orders of notifications. For example,Sensor 106 has three notification targets: 214-244-5555,mail@domain.com, and 214-244-9889. Items 214-244-5555 andmail@domain.com are to occur simultaneously as indicated by appearing onthe same line together, separated by a comma. Item 214-244-9889 is tooccur after the first step is completed. Step 1 shows notification of214-244-5555 via SMS and simultaneously notification at mail@domain.com.Step 2 may or may not be configured to have a delay before execution ofan SMS to 215-244-9889. In each case, the SMS text may encodeinformation such as, “Sensor 106 threshold exceeded”. The email mayincorporate a similar wording.

Additionally, the system may be configured to send additionalinformation configured by notification method. Sensor 106, SMS for214-244-5555 is configured to send Sensor Info (eg, what Sensor numberand threshold triggered), email (short video of what has transpired atSensor 106), or a jpg snapshot of that relative moment in time.

Upon receipt of the alarm notification, the system may be setup to allowfor acknowledgement of receipt of the notification. The recipient of theSMS may reply as in the course of a normal SMS texting dialog with theaction the system is to take. For example, the recipient may SMS back,“Reset”, or “Notify alarm service”, “Turn on camera recorder”, or “Sendvideo” or other such keyword/action definitions as deemed necessary andimplemented within the system.

Systems and methods have been shown and/or described in the aboveembodiments for alerting events to mobile users based on geographicallocations. Although the above descriptions set forth preferredembodiments, it will be understood that there is no intent to limit theinvention by such disclosure, but rather, it is intended to cover allmodifications and alternate implementations falling within the spiritand scope of the invention. Furthermore, the embodiments are intended tocover capabilities and concepts whether they be via a loosely coupledset of components or they be converged into one or more integratedcomponents, devices, circuits, and/or software programs.

FIG. 11 depicts a Browser Alert System Interface. Various sensors 106,106 a, 106 b, 108, a peak value change (or delta) within a certainamount of time (in seconds or even minutes), contact information as wellas a method for notification.

What is claimed is:
 1. A method for receiving an alert of an event by amobile device, comprising: identifying the event via a remote eventalert server based on a type of the event and a location occurrence ofthe event; and receiving the alert of the event at at least one mobiledevice if the event is a specific event and if the at least one mobiledevice is located at or near a geographical location; wherein receivingthe alert of the event at the at least one mobile device comprises:performing a lookup of the at least one mobile device associated with atleast one service provider site; and sending the alert to the at leastone mobile device based on a period of time the at least one mobiledevice is registered with the at least one service provider site and ifthe at least one mobile device is within a predetermined distance of theevent based on the location.
 2. The method of claim 1, comprisingcapturing information about the event by the at least one mobile device,the information comprising location information and event typeinformation.
 3. The method of claim 2, wherein the occurrence of theevent is above a predetermined threshold.
 4. The method of claim 1,wherein if the event is a specific event and if the event occurred at ornear the geographical location comprises at least one of: processinginformation related to the event, wherein the processing comprises:recognizing an image from the information about the event; identifying atype of the event based on the image; and identifying a location of theevent based on a location of the at least one mobile device.
 5. Themethod of claim 1, wherein receiving the alert of the event at the atleast one mobile device comprises at least one of: performing a lookupof the at least one mobile device associated with at least one serviceprovider site; and sending the alert to the at least one mobile deviceassociated with at least one service provider site.
 6. The method ofclaim 1, comprising sensing by a sensor an occurrence of the event. 7.The method of claim 1, wherein receiving the alert of the event at theat least one mobile device comprises at least one of: sending the alertto at least one service provider site; and forwarding the alert from theat least one service provider site to the at least one mobile deviceassociated with the at least one service provider site.
 8. The method ofclaim 1, wherein receiving the alert of the event at the at least onemobile device comprises at least one of: identifying a location of atleast one service provider site from a geographical information system;sending the alert to the at least one service provider site within apredetermined distance of the event based on the location; andforwarding the alert from the at least one service provider site to theat least one mobile device associated with the at least one serviceprovider site.
 9. The method of claim 1, wherein receiving the alert ofthe event at the at least one mobile device comprises at least one of:sending a first alert to a first mobile device moving towards the event;and sending a second alert to a second mobile device moving away fromthe event.
 10. The method of claim 1, wherein at least one of the firstmobile device and the second mobile device is the at least one mobiledevice.
 11. A non-transitory computer readable storage medium comprisinginstructions, for receiving an alert of an event by at least one mobiledevice, that when executed by a processor cause the processor toperform: monitoring a geographical area via the at least one mobiledevice; identifying the event via an event alert server based on a typeof the event and a location occurrence of the event; and receiving thealert of the event at the at least one mobile device if the event is aspecific event and if the at least one mobile device is located at ornear the geographical area; wherein receiving the alert of the event atthe at least one mobile device comprises: performing a lookup of the atleast one mobile device associated with at least one service providersite; and sending the alert to the at least one mobile device based on aperiod of time the at least one mobile device is registered with the atleast one service provider site and if the at least one mobile device iswithin a predetermined distance of the event based on the geographicalarea.
 12. A network that receives an alert of an event by a mobiledevice, comprising: a remote event alert system configured to: detect anoccurrence of the event, identify the event based on a type of the eventand a location occurrence of the event, and receive the alert of theevent at at least one mobile device if the event is a specific event andif the at least one mobile device is located at or near a geographicallocation; wherein the alert of the event being received at the at leastone mobile device comprises: a lookup of the at least one mobile deviceassociated with at least one service provider site being performed; andthe alert to the at least one mobile device being sent based on a periodof time the at least one mobile device is registered with the at leastone service provider site and if the at least one mobile device iswithin a predetermined distance of the event based on the location. 13.The network of claim 12, further comprising at least one event monitor,wherein the at least one event monitor is operable to perform at leastone of: sense an occurrence of the event, determine if the event isabove a predetermined threshold, and wherein the event monitor isoperable to notify the event alert system of the occurrence of the eventif the event is above the predetermined threshold.
 14. The network ofclaim 12, wherein the event alert system is further operable to performat least one of: a lookup of at least one mobile device associated withat least one service provider site, and send the alert to the at leastone mobile device associated with the at least one service providersite.
 15. The network of claim 12, wherein the event alert system isfurther operable to send the alert to at least one service providersite.
 16. The network of claim 15, wherein the event alert system isfurther operable to cause the at least one service provider site toforward the alert from the at least one service provider site to the atleast one mobile device associated with the at least one serviceprovider site.
 17. The network of claim 12, wherein the at least onemobile device is configured to capture information about the event by asensor communicably coupled to the at least one mobile device, theinformation comprising location information and event type information.18. The network of claim 12, further comprising at least onegeographical information system, wherein the event alert system isfurther operable to perform at least one of: identify a location of atleast one service provider site from the at least one geographicalinformation system, send the alert to the at least one service providersite within a predetermined distance of the event based on the location,and forward the alert from the at least one service provider site to theat least one mobile device associated with the at least one serviceprovider site.
 19. The network of claim 12, further comprising: at leastone image recognition system; and at least one geographical informationsystem, wherein the at least one image recognition system is operable toperform at least one of: recognize an image from the information aboutthe event, the event alert system further operable to identify a type ofthe event based on the image, and identify a location of the event basedon a location of the at least one mobile device from the at least onegeographical information system.
 20. The network of claim 12, whereinthe event alert system is further operable to perform at least one of:register at least one mobile user associated with the at least onemobile device; monitor a specific event; determine if the monitoredevent is the specific event based on a type of the event and a locationof the event; and send an alert of the event to the at least one mobiledevice if the event is the specific event.